home *** CD-ROM | disk | FTP | other *** search
-
-
-
- ssssttttrrrreeeeaaaammmmttttaaaabbbb((((DDDD4444)))) ssssttttrrrreeeeaaaammmmttttaaaabbbb((((DDDD4444))))
-
-
-
- NNNNAAAAMMMMEEEE
- _ssss_tttt_rrrr_eeee_aaaa_mmmm_tttt_aaaa_bbbb - STREAMS driver and module declaration structure
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_ssss_tttt_rrrr_eeee_aaaa_mmmm_...._hhhh_>>>>
- _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_dddd_dddd_iiii_...._hhhh_>>>>
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- The _ssss_tttt_rrrr_eeee_aaaa_mmmm_tttt_aaaa_bbbb structure is made up of pointers to _qqqq_iiii_nnnn_iiii_tttt structures for
- both the read and write queue portions of each module or driver.
- (Multiplexing drivers require both upper and lower _qqqq_iiii_nnnn_iiii_tttt structures.)
- The _qqqq_iiii_nnnn_iiii_tttt structure contains the entry points through which the module or
- driver routines are called.
-
- UUUUSSSSAAAAGGGGEEEE
- Each STREAMS driver or module must have a _ssss_tttt_rrrr_eeee_aaaa_mmmm_tttt_aaaa_bbbb structure. The
- _ssss_tttt_rrrr_eeee_aaaa_mmmm_tttt_aaaa_bbbb structure must be named _p_r_e_f_i_x_iiii_nnnn_ffff_oooo, where _p_r_e_f_i_x is the driver
- prefix.
-
- SSSSttttrrrruuuuccccttttuuuurrrreeee DDDDeeeeffffiiiinnnniiiittttiiiioooonnnnssss
- The _ssss_tttt_rrrr_eeee_aaaa_mmmm_tttt_aaaa_bbbb structure contains the following members:
- _ssss_tttt_rrrr_uuuu_cccc_tttt _qqqq_iiii_nnnn_iiii_tttt _****_ssss_tttt______rrrr_dddd_iiii_nnnn_iiii_tttt_;;;; _////_**** _rrrr_eeee_aaaa_dddd _qqqq_uuuu_eeee_uuuu_eeee _****_////
- _ssss_tttt_rrrr_uuuu_cccc_tttt _qqqq_iiii_nnnn_iiii_tttt _****_ssss_tttt______wwww_rrrr_iiii_nnnn_iiii_tttt_;;;; _////_**** _wwww_rrrr_iiii_tttt_eeee _qqqq_uuuu_eeee_uuuu_eeee _****_////
- _ssss_tttt_rrrr_uuuu_cccc_tttt _qqqq_iiii_nnnn_iiii_tttt _****_ssss_tttt______mmmm_uuuu_xxxx_rrrr_iiii_nnnn_iiii_tttt_;;;; _////_**** _llll_oooo_wwww_eeee_rrrr _rrrr_eeee_aaaa_dddd _qqqq_uuuu_eeee_uuuu_eeee_****_////
- _ssss_tttt_rrrr_uuuu_cccc_tttt _qqqq_iiii_nnnn_iiii_tttt _****_ssss_tttt______mmmm_uuuu_xxxx_wwww_iiii_nnnn_iiii_tttt_;;;; _////_**** _llll_oooo_wwww_eeee_rrrr _wwww_rrrr_iiii_tttt_eeee _qqqq_uuuu_eeee_uuuu_eeee_****_////
-
- The _ssss_tttt______rrrr_dddd_iiii_nnnn_iiii_tttt field contains a pointer to the read-side _qqqq_iiii_nnnn_iiii_tttt structure.
- For a multiplexing driver, this is the _qqqq_iiii_nnnn_iiii_tttt structure for the upper read
- side.
-
- The _ssss_tttt______wwww_rrrr_iiii_nnnn_iiii_tttt field contains a pointer to the write-side _qqqq_iiii_nnnn_iiii_tttt structure.
- For a multiplexing driver, this is the _qqqq_iiii_nnnn_iiii_tttt structure for the upper
- write side.
-
- The _ssss_tttt______mmmm_uuuu_xxxx_rrrr_iiii_nnnn_iiii_tttt field contains a pointer to the lower read-side _qqqq_iiii_nnnn_iiii_tttt
- structure for multiplexing drivers. For modules and non-multiplexing
- drivers, this field should be set to _NNNN_UUUU_LLLL_LLLL.
-
- The _ssss_tttt______mmmm_uuuu_xxxx_wwww_iiii_nnnn_iiii_tttt field contains a pointer to the lower write-side _qqqq_iiii_nnnn_iiii_tttt
- structure for multiplexing drivers. For modules and non-multiplexing
- drivers, this field should be set to _NNNN_UUUU_LLLL_LLLL.
-
- RRRREEEEFFFFEEEERRRREEEENNNNCCCCEEEESSSS
- _qqqq_iiii_nnnn_iiii_tttt(D4)
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-